fix: correct syntax generation for column types with parameters #5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, the mapToLaravelType() method was returning malformed
strings like 'char, 10' which resulted in invalid migration syntax:
$table->char, 10('column_name');
This commit refactors the method to return an array structure
containing the method name and parameters separately, allowing
proper syntax generation:
$table->char('column_name', 10);
$table->string('column_name', 255);
$table->decimal('column_name', 8, 2);
Changes:
Tested with MySQL CHAR(10), VARCHAR(255), DECIMAL(8,2) columns"